Oh, maybe add a .nix entry to .editorconfig so our editors follow the appropriate standard if we ever update flake.nix.

Ready to merge

@o2sh we forgot something important. flake.lock pinned nixpkgs, so after a week or less commit get outdated and lock should be refreshed. I have no idea how to work with Workflows yet so i leave this to you. Flake.lock should be updated approximately once in 10 days

Good point, @Sk7Str1p3. I've reverted the PR for now.

On second thought, it might not be ideal to commit these files directly to the repo since they’re tied to a specific setup (Nix).

Instead, we could add a section in the Wiki for Nix users, including the flake.nix file along with some explanations.

@o2sh we forgot something important. flake.lock pinned nixpkgs, so after a week or less commit get outdated and lock should be refreshed. I have no idea how to work with Workflows yet so i leave this to you. Flake.lock should be updated approximately once in 10 days

Could it just be added to the gitignore? We're not like an enterprise team with strict environment requirements, so I think it would be reasonable to just let the dev shell users manage their own lock file.

Yep, we could left lock out. Also we could set workflows for updating lock. I found few solutions with that already

https://github.com/DeterminateSystems/update-flake-lock this seems to be best solution as it comes from Nix developers

In the meantime, I've created a page in the wiki explaining how to setup a local dev environment for onefetch using Nix: https://github.com/o2sh/onefetch/wiki/nix-local-setup

Hope that's okay with you @Sk7Str1p3

Yep that's okay

We could probably add .envrc and flake.nix to the .gitignore so nobody accidentally commits them, then

@o2sh im willing come back with much greater and comprehensive nix toolchain. Crane is library around nix with devShell, automatic tests generator and incremental builds, it also should support cachix which would not even build crates locally but simply download pre-built crates leading to much faster builds.
flake.lock won't be a problem because of workflows (renovate/determinate)

I think the Helix editor has a flake devshell configured, so we could probably just do what they do

Helix flake not using all Nix features, I feel like they added it just 'for the sake of it'.
Also, I found out why I had issues with rmeta files, and it's not filesystem issue but nix module feature. Impermanence is commonly used setup which allows to remove all files on reboot except ones set in configuration. The main problem is it 'core' - it uses bindmounts and symlinks, and bindmounts somehow caused my problems.
Crane is able solve all this issues by building to /nix/store